Apex Legends\Respawn Entertainment

Apex Legends Engine Error — How to Fix FS_CheckAsyncRequest Crash

There isn't currently a perfect fix for the FS_CheckAsyncRequest crash message in Apex Legends, but some players are finding success with fresh installs, validating files or switching to DX11.

Author:
Robbie Landis
Publish date:
May 23, 2023 1:24 PM EDT

Engine Error FS_CheckAsyncRequest in Apex Legends Remove Players from Lobbies

This engine error is removing players from Apex Legends lobbies and preventing them from rejoining causing abandonment penalties.
The error has been known and reported in the past, with EA Help Forums providing a few different fixes for the issue.
EA’s suggested fixes don’t work for everyone and there doesn’t seem to be a consistent cause for it.

Players in Apex Legends are used to dealing with bugs and glitches, such as not being able to properly spawn on control points in the Mixtape mode Control. It gets even more frustrating when these bugs potentially stop you from playing the game like a recent Engine Error prompting the message, “FS_CheckAyncRequest returned error for model” as reported by Reddit User olm4te.

What Does Engine Error CheckAsyncRequest Do?

The Reddit user reported that after getting this error they were kicked out of their matches, couldn’t rejoin and then were given a penalty for abandoning the game. This can be one of the most frustrating kinds of bugs in Apex Legends, especially if you’re trying to play competitively and end up getting penalized for something entirely out of your control.

Various other Reddit users chimed in to say that they’re suffering from the same problem and can’t seem to figure out exactly what causes it. They’ve reported it happening on multiple different maps, several times in a single play session.

How Do You Fix Engine Error CheckAsyncRequest?

The bad news is, there doesn’t seem to be a perfect fix for this Engine Error CheckAsyncRequest just yet. Despite players suddenly running into it more often, it’s actually been present since at least April 2020.

A user recently reported the problem on EA’s Help Forum on April 20th and was given a workaround to try and solve the problem. Though it seems these fixes don’t work for everyone.

According to Apex Legends on Twitter, it’s an issue the team is aware of and looking into. In the meantime, it may have something to do with the DX12 version of Apex Legends. They suggest switching to the DX11 version or changing to a higher model detail as a temporary fix.

Some users report validating files through Steam or doing a fresh install seems to help the issue, while others say that it keeps happening and are still looking for a fix.